Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

XCODE utility

Encrypts Progress 4GL procedures and include files using either the default or a specified encryption key.

Syntax

SYNTAX

xcode [ -k key ] [ -d directory ] { files | - }

key

The encryption key. The key is an ASCII character string up to eight characters long. If key is not supplied, the default key supplied by OpenEdge is used.

directory

The directory where the encrypted files are placed. The specified directory must be different from the source directory, because each encrypted file retains the name of its original source file. Existing files in directory are overwritten only if they are encrypted.

files

The relative pathnames of files to be encrypted. The pathnames supplied are appended to directory. Therefore, you should build a directory structure exactly parallel to the source directory structure, move to the source root, and specify relative pathnames.

- SYS$INPUT

Indicates that source filenames are to be read from standard input.

Example

cd /applr001 xcode -k key1 -d applx001 *.p

find applf002/*.p | xcode -k key2 -d applx002 -

Notes

You must create the full directory structure desired for your encrypted files before running XCODE; XCODE does not create any directories implied by directory or files.
The encryption algorithm is based on known techniques; therefore, the code is breakable. If your source code is highly sensitive, consider additional security methods.
Encrypted include files must use the same key as any procedure that includes them.
Compile encrypted procedures with the XCODE option on the COMPILE statement. (The XCODE option is not required if the procedures were encrypted with the default key.) The XCODE option requires the same key used with the XCODE utility. OpenEdge Development: Progress 4GL Reference describes the COMPILE statement in detail.